The DBMS must notify appropriate individuals when accounts are terminated.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-52199	O112-C2-020700	SV-66415r3_rule		Medium

Description
When application accounts are terminated, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events that affect user accessibility and application processing, applications must notify the appropriate individuals when an account is terminated so they can investigate the event. Such a capability greatly reduces the risk that application accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes. Note that user authentication and account management must be done via an enterprise-wide mechanism whenever possible. Examples of enterprise-level authentication/access mechanisms include, but are not limited to, Active Directory and LDAP. This requirement applies to cases where accounts are directly managed by Oracle. Notwithstanding how accounts are normally managed, the DBMS must support the requirement to notify appropriate individuals upon account termination within Oracle. Indeed, in a configuration where accounts are managed externally, the manipulation of an account within Oracle may indicate hostile activity.

Description

When application accounts are terminated, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events that affect user accessibility and application processing, applications must notify the appropriate individuals when an account is terminated so they can investigate the event. Such a capability greatly reduces the risk that application accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes. Note that user authentication and account management must be done via an enterprise-wide mechanism whenever possible. Examples of enterprise-level authentication/access mechanisms include, but are not limited to, Active Directory and LDAP. This requirement applies to cases where accounts are directly managed by Oracle. Notwithstanding how accounts are normally managed, the DBMS must support the requirement to notify appropriate individuals upon account termination within Oracle. Indeed, in a configuration where accounts are managed externally, the manipulation of an account within Oracle may indicate hostile activity.

STIG	Date
Oracle Database 11.2g Security Technical Implementation Guide	2016-12-15

Details

Check Text ( C-54257r1_chk )
Check DBMS settings to determine whether it will notify appropriate individuals when accounts are terminated. If the DBMS does not notify appropriate individuals when accounts are terminated, this is a finding.

Fix Text (F-57017r3_fix)
Working with the DBA and site management, determine the appropriate individuals (by job role) to be notified. If Oracle Audit Vault is available, configure it to notify the appropriate individuals when accounts are terminated. If Oracle Audit Vault is not available, configure the Oracle DBMS's auditing feature to record account-termination activity. Create and deploy a mechanism, such as a frequently-run job, to monitor the audit table or file for these records and notify the appropriate individuals.

Fix Text (F-57017r3_fix)

Working with the DBA and site management, determine the appropriate individuals (by job role) to be notified.

If Oracle Audit Vault is available, configure it to notify the appropriate individuals when accounts are terminated.

If Oracle Audit Vault is not available, configure the Oracle DBMS's auditing feature to record account-termination activity. Create and deploy a mechanism, such as a frequently-run job, to monitor the audit table or file for these records and notify the appropriate individuals.